Live video broadcast user interface

ABSTRACT

In an example embodiment, an indication is received via a user interface in a first mobile device to begin recording live video on the first mobile device. Then the recording of live video is begun by the first mobile device in response to the receiving of the indication. The live video is displayed in the user interface as it is being recorded. A gesture by a user of the first mobile device is detected. In response to the detection of the gesture, the broadcasting of the live video as it is being recorded to a plurality of mobile devices other than the first mobile device is begun. Then, in the user interface along with the live video, identifications of a plurality of users corresponding to the plurality of mobile device other than the first mobile device to which the live video is being broadcast are displayed.

CROSS-REFERENCE TO RELATED PATENT DOCUMENTS

This patent application is a continuation of and claims the benefit ofpriority to U.S. patent application Ser. No. 13/851,606, entitled “USERINTERFACE FOR SIMULTANEOUS DISPLAY OF VIDEO STREAM OF DIFFERENT ANGLESOF SAME EVENT FROM DIFFERENT USERS,” filed Mar. 27, 2013, which is acontinuation of and claims the benefit of priority to U.S. patentapplication Ser. No. 13/398,227, entitled “CONTENT SHARING VIA SOCIALNETWORKING,” filed Feb. 16, 2012, now U.S. Pat. No. 8,412,772, issuedApr. 2, 2013, which claims the benefit of priority to U.S. ProvisionalApplication No. 61/537,526, entitled “CONTENT SHARING VIA SOCIALNETWORKING,” filed Sep. 21, 2011, the benefit of priority to each ofwhich is claimed hereby, and each of which are incorporated by referenceherein in its entirety.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure as it appears in the United States Patent andTrademark Office patent files or records, but otherwise reserves allcopyright rights whatsoever. The following notice applies to thesoftware and data as described below and in the drawings that form apart of this document: Copyright 2012, Color Labs, Inc. All RightsReserved.

TECHNICAL FIELD

This application relates generally to the communication of content and,more specifically, to systems and methods for the sharing of contentfacilitated via social networking.

BACKGROUND

An ever-increasing use of the Internet is the sharing among users ofcontent, such as video clips, audio segments, photographs, and the like.Many mechanisms exist for such sharing, from direct transfer of suchcontent from one user to another, such as by way of e-mail, to theposting of such content on a website so that the content may beavailable to visitors of the website. The capabilities of the Internetand associated communication devices have evolved so that more advancedforms of content sharing, including one-on-one video conferencing, suchas by way of Skype® and other mechanisms, have become more commonplace.

An innovation of the Internet that has also become popular among usersis the creation of human “social” networks, such as Facebook® andMyspace®. In such a network, friends, acquaintances, and other types ofhuman relationships may be explicitly specified, allowing connected orassociated users to stay apprised of the current status and ongoingactions of each other. Such status may also include content, such asphotographs, posted by one user to be viewed by other connected users.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which:

FIG. 1 is a block diagram illustrating an example communication system;

FIG. 2 is a block diagram illustrating modules of an example host and/orvisiting device of an example communication system;

FIG. 3 is a block diagram illustrating modules of an example server ofan example communication system;

FIGS. 4A, 4B, and 4C are communication diagrams illustrating examplemethods for sharing content via social network interaction.

FIG. 5 is a block diagram of an example content distribution systemassociated with an example communication system;

FIGS. 6A through 6J are example screenshots of an example user interfaceof an example application executing on a host and/or visiting device forthe sharing of content;

FIGS. 7A through 7O are example screenshots of an example web-based userinterface being viewed on a visiting device for the sharing of content;and

FIG. 8 is a diagrammatic representation of a machine in the example formof a computer system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed.

DETAILED DESCRIPTION

Example methods and systems for sharing content, such as photographs,audio content, video content, textual content, graphical content, andthe like, via a social network are discussed. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding of exampleembodiments. It will be evident, however, to one skilled in the art thatthe present subject matter may be practiced without these specificdetails. It will also be evident that the particular types of systemsand methods described herein are not limited to the examples providedand may include other scenarios not specifically discussed.

In accordance with an example embodiment, FIG. 1 illustrates an examplecommunication system 100 for the sharing of content 120 among multipleusers. The content 120 may be any content generated or captured by auser that is of interest to another user, including, but not limited to,video content, audio content, audio/video content, textual or graphicalcontent, and photographs or still photo images. Types of textual orgraphical content may include, for example, textual or map dataindication a location of a user as determined by electronic signals,environmental data, and other inputs that may be captured by a userdevice. In one implementation, the capture of the content 120 may beongoing while the content 120 is being shared or distributed within thecommunication system 100.

The communication system 100 includes at least one host device 102 andmultiple visitor devices 104A, 104B, 104C (collectively or individually,104) associated with users or members of a social network 110 that sharecontent by way of a communication network 106. Examples of the socialnetwork 110, or the infrastructure supporting such a network 110,include, but are not limited to, Facebook® and Myspace®. In otherexamples, other devices not strictly associated with the social network110 may also send or receive the content 120 via the communicationnetwork 106.

Examples of the communication network 106 may include, but are notlimited to, any and/or all of a wide-area network (such as theInternet), a local-area network (LAN) (such as an IEEE 802.11x (Wi-Fi)network), a Bluetooth connection, a Near Field Communication (NFC)connection, an Ethernet connection, a mobile or cellular communicationsdevice network (such as a third generation (3G) or fourth generation(4G) connection), and a microcell network, or combinations thereof. Thecommunication network 106 may include one or more servers, such as webor API servers, content distribution servers, and the like, as isdescribed in greater detail below, one or more of which may support theoperation of the social network 110. In some examples, the communicationnetwork 106 may include any number of transmitters, receivers, switches,repeaters, and other components to facilitate communication between thehost device 102 and the visiting devices 104.

As shown in FIG. 1, the host device 102 provides or sources the content120 by way of the communication network 106 to one or more visitordevices 104 for presentation or display to the users of the visitordevices 104. In some implementations, each of the host device 102 and/orthe visitor devices 104 may be any communication device capable ofgenerating, capturing, transmitting, and/or receiving the content 120.Examples of the host device 102 and the visitor devices 104 include, butare not limited to, smart phones, personal digital assistants (PDAs),desktop computers, laptop computers, netbook computers, tabletcomputers, gaming systems, and televisions. While FIG. 1 displays asingle host device 102 and three member visitor devices 104, any numberof host devices 102 and visitor devices 104 may share multiple items orstreams of content 120 via the communication network 106. In manyinstances, a single user device may operate as both a host device 102that provides content 120, and as a visitor device 104 that receivescontent 120, at various times, or even concurrently or simultaneous.

In at least some examples, the communication system 100 employs thesocial network 110 or associated access site to notify users ofpotential visitor devices 104 of the availability of content 120 beinghosted by a host device 102 automatically in a timely manner. Apotential reason for employing the social network 110 in this capacityis that users most likely to be interested in receiving the content 120may be those that are connected to the user of the host device 102 insome way, such as friends, family members, or acquaintances, as may beindicated by way of the social network 110. Additionally, comments orother indications, such as “likes”, regarding the content 120 may beeasily provided via the same social network 110. Other potentialadvantages may be discerned from the various embodiments described ingreater detail below.

As employed herein, a host may be any user or some other identifiableentity or organization that may source the content 120 to be shared. Forexample, a news agency capable of streaming video content, and that mayalso maintain a presence on the social network 110, may be considered ahost. Likewise, a visitor may be any user, entity, or organization thatmay “visit” a host by receiving the content 120 being generated ortransmitted by that host.

FIG. 2 is a block diagram of an example embodiment of a host and/orvisitor (or user) device 200 that may serve as one of the host devices102 and/or visitor devices 104 depicted in FIG. 1. The user device 300may include a number of software and/or hardware modules, such as a userinterface module 202, a location services module 204, an environmentdetection module 206, a content caching module 208, a content pushmechanism module 210, a content ingestion module 212, and a socialnetwork interface module 214. In other user devices 200, one or more ofthe modules 202-214 may be omitted, and one or more modules not depictedin FIG. 2 may be included. In one example, the modules 202-214 may besoftware modules that constitute at least part of an application beingexecuted by one or more processors on the user device 200. Moregenerally, the modules 202-214 may be hardware, software, firmware, orsome combination thereof.

In the user device 200, the user interface module 202 may facilitatevarious operations for the sharing and receiving of content 120 by theuser of the host/visitor device 200, as well as access to the socialnetwork 110 employed to facilitate the content sharing. As discussedmore fully below, these aspects may include, but are not limited to, therequest or approval of the sharing of content 120, the actual capture,generation, and/or viewing of the content 120, and the specification bya user of the types of content 120 or possible hosts of content 120 ofinterest to the user, as well as any interfacing with the social network110 performed in conjunction with the sharing of content 120. Morespecific examples of the user interface provided by the user interfacemodule 202 are discussed in greater detail below in conjunction withFIGS. 6A through 6J and FIGS. 7A through 7O.

The location services module 204 may provide or generate informationregarding the physical location of the user device 200. In one example,the location services module 204 may determine location by way ofsignals received from a Global Positioning System (GPS), an Assisted GPS(A-GPS), a Wi-Fi Positioning System, and/or cell-site triangulation. Thelocation services module 204 may receive such signals by way ofcircuitry of the user device 200 and process one or more of the signalsto determine the location. As described below, this location informationmay be used to determine if and when content 120 may be offered forreception by other users.

The environment detection module 206 may receive signals from one ormore sensors residing on, or in communication with, the user device 200to indicate various environmental conditions in the vicinity of the userdevice 200. Such signals may indicate, for example, atmosphericpressure, temperature, light, velocity, acceleration, orientation, andso on, as generated by sensors such as light meters, accelerometers,gyroscopes, thermometers, and the like. For example, persistent changesin acceleration may indicate the client device is located in a movingcar, or the detection of multiple voices may indicate presence within acrowd. The environment detection module 206 may also employ signals fromvarious communication network interfaces, such as Near-FieldCommunication (NFC) signals, Bluetooth® communication signals, Wi-Ficommunication signals, and the like to supplement and enhance thelocation information of the user device 200 generated by the locationservices module 206 to more closely define the location of the userdevice 200.

The content caching module 208 may store locally on the user device 200content 120 that has been captured at the user device 200 but has notbeen transmitted to the communication network 106 for sharing with otheruser devices 200, such as during times when the user device 200 has lostcontact with the communication network 106. In response to theconnection between the communication network 106 and the user device 200being restored, the cached content, including photos, audio, video,textual data, graphical data, and the like, may then be uploaded to aserver or other node of the communication network 106 for subsequenttransfer to the other user devices 200.

The content push mechanism module 210 facilitates the reception ofcontent 120 at the device 200 operating as a visitor device 200 from adistribution server or other device of the communication network 106under a “push” data transfer model. For example, a Comet web applicationmodel may be employed to receive content 120 and other data under a“hanging GET” protocol, in which the server maintains a HyperTextTransfer Protocol (HTTP) request from the user device 200 indefinitelyto push the content 120 to the user device 200.

The content ingestion module 212 may be responsible for taking thecontent 120 captured at the user device 200 and possibly modifying,adjusting, or otherwise processing the content 120 before sharing thedata via the communication network 106. For still image content 120,examples of such processing may include, but are not limited to, scalingthe image, and adjusting the resolution, orientation, brightness,sharpness, color, contrast, or focus of the image. These operations maydepend on several factors, including, but not limited to, the captureand display capabilities of the user device 200, and the speed of thecommunication network 106 coupling the user device 200 with other userdevices 200. The content ingestion module 212 may also package variousmetadata with the content 120, such as the location and environmentaldata discussed above.

The social network interface module 214 may facilitate the transfer ofinformation, as well as the processing of that information, between anapplication executing on the user device 200 and the social network 110.Such information may include, for example, “friends”, family members,and/or acquaintances of users as denoted in the social network 110, aswell as their current status, possibly including their current location.This information may be utilized to ascertain potential visitors for ahost of content 120. In some examples, comments, “likes”, and similarinformation regarding a visitor's view of content 120 or a host of thatcontent 120 may also be maintained by the social network 110 to provideinformation to other potential visitors of content 120 or a host of thatcontent 120. Other information may also be transmitted between thesocial network 110 and the application in other embodiments. Inaddition, the application may allow a user of the device 200 executingthe application to log-on to the social network 100 and perform a numberof social-network-related functions via the application.

FIG. 3 is a block diagram of an example embodiment of a server device300 located within, or coupled with, the communication network 106 ofFIG. 1. In at least some examples, the server device 300 may facilitateactivities regarding the transmission of content 120 between userdevices 200, including, for example, the determination of potentialvisitors via the social network 110, as well as the initiation andcontinued control of the transmission of content 120 between the userdevices 200. In various examples, the service device 300 may be anApplications Programming Interface (API) server, a web server, oranother type of server capable of performing the various operationsdescribed herein.

The server device 300 may include a number of software and/or hardwaremodules, such as an API module 302, a user preferences module 304, asocial network contacts module 306, a host/visitor status module 308, acontent push mechanism module 310, a distribution server selectionmodule 312, a content storage module 314, and an incentive/award module316. In other server devices 300, one or more of the modules 302-316 maybe omitted, and one or more modules not depicted in FIG. 3 may beincluded. In one example, the modules 302-316 may be software modulesthat constitute at least part of an application being executed by one ormore processors on the server device 300. More generally, the modules302-316 may be hardware, software, firmware, or some combinationthereof. Further, the server device 300 may be embodied in multipleseparate devices that form a system capable of accomplishing theoperations of the server device 300 as described herein.

The API module 302 may facilitate communications between the serverdevice 300 and multiple user devices 200 and/or the social network 110for a variety of purposes. Such purposes may include, but are notlimited to, the collection of information from the social network 110for determining possible hosts of the content 120 and potential visitorsfor those hosts, information regarding the perception of visitors of aparticular host or associated content 120, and communication between theserver device 300 and the user devices 200 regarding the initiation andcontrol of the actual sharing of content 120 among the user devices 200.

The user preferences module 304 acquires and maintains data associatedwith the preferences of potential hosts and visitors of content 120regarding the transmission and reception of the content 120. Forexample, the user preferences module 304 may maintain data generatedfrom user responses in association with the first execution of anapplication employed in the user device 200 to facilitate the sharing ofcontent 120. Explicit user preferences may also be retrieved at othertimes by way of the application in other examples. Examples of such userpreferences are described more fully below in conjunction with FIG. 4C.

One type of user preference data may include the types of content 120 inwhich each potential visitor may be interested. The types of content 120may refer to, for example, the format of the content 120 (for example,video, audio, textual, graphical, and so on), the subject matter of thecontent 120 (for example, sports-related, news-related, family-related,friend-related, and so forth), and other factors associated with thecontent 120. In one example, the user may indicate a preference forparticular content 120 by way of “liking” the content 120, or providingpositive comments regarding the content 120, as mentioned above.

Another type of preference data may not be explicitly specified by theuser, but is instead derived from previous user actions, such asprevious content 120 viewed, previous hosts visited, previous websitesviewed, days of the week or times of the day during which such useractions occurred, user activities in connection with the social network110 (FIG. 1), and so forth.

In some implementations, the user preference information may be employedto automatically present certain types of content 120, or content 120from certain hosts, to the user without prompting the user for approval.In other examples, the preference information may be used to inform theuser of content 120 in which the user may be interested, and query theuser as to whether they desire to visit the host associated with thecontent 120. In yet other situations, the preference information mayprevent certain content 120 from being offered to the user, such as whenthe user has explicitly indicated a lack of interest in such content120, or in any content 120 from a particular host designated by theuser.

The social network contacts module 306 may retrieve data from the socialnetwork 110 identifying friends, family, likes, and so on for eachpotential visiting user. Further, this data may be updated by way ofretrieving the information periodically from the social network 110. Forexample, the data may indicate hosts and their associated potentialvisitors based on friends, family, and other acquaintances as indicatedin the social network 110. The social network contacts module 306 mayalso identify other potential visitors for any particular hosts based oncommonalities or other factors possibly linking a host and a potentialvisitor, including, but not limited to, related educational backgrounds,business associations, social interests, and the like. In anotherexample, relationships other than those specifically designated by thesocial network 110, such as friends of friends, friends of familymembers, and the like, may be regarded as potential visitors for eachpossible host of content 120. Conversely, the social network contactsmodule 306 may track potential hosts for a user in a possible visitorrole in a way similar to that described above.

The host/visitor status module 308 may maintain current information, andpossibly historical data, regarding the status of each user device 200.This information may include, for example, the current geographiclocation of each user device 200, as well as previous locations of thedevice 200. As indicated above, such data may be provided by thelocation services module 204 and/or the environment detection module 206of each user device 200.

With respect to content sharing, the host/visitor status module 308 maymaintain information regarding current and/or former visitations fromboth a host and a visitor standpoint. Such information may include theformat, subject matter, and other aspects of the content 120 transmittedor received, the visitors or host associated with the content 120 beingshared, any particular distribution servers employed to forward thecontent 120 from the host to the visitor, and the like.

As will be described in greater detail below, this status informationmay be utilized to determine whether a host is currently sharing content120 (and, thus, possibly available to continue to share that content 120with other visitors), whether the host has performed some kind of actionor “gesture” via the user device 200 of the host which would indicatethat the host may be in a position to share content 120 with one or morepotential visitors, and identify which potential visitors may beinterested in receiving the content 120.

The content push module 310 may provide the functionality for the serverdevice 300 to push content to the visitor devices 200 of a particulargroup 110. As mentioned above, the pushing of content 120 may befacilitated by way of a Comet web application model to distributecontent 120 and other data to the client devices 300 under a “hangingGET” protocol. In another example, the functionality of the content pushmodule 310 may provided by way of a separate service device, such as aserver device specifically allocated to perform the distribution of thecontent 120 from a host device to a visitor device.

The distribution server selection module 312 may select a distributionserver from a group of such servers to perform the content 120distribution from a host to one or more visitor devices 200. In oneexample, the group of servers may define a distribution server “farm”provided primarily for content distribution. To perform the selection,the distribution server selection module 312 may access informationregarding an item or stream of content 120 to be distributed to a newvisitor requesting the content 120. Depending on the current number ofvisitors being serviced by each of the distribution servers, possibly inaddition to other factors, the distribution server selection module 312may select a distribution server currently servicing other visitors or anew distribution server from the group to provide the content 120 to thenew visitor.

The content storage module 314 may store and manage content 120 that isyet to be distributed to one or more visitor user devices 200. Forexample, the content push module 310 may allow visitor devices 200 thatare in the process of receiving content 120 while employing the serverdevice 300 in a digital video recorder (DVR) mode in which pausing,rewind, fast-forward, and similar playback modes are provided. Thecontent storage module 314 may also provide a complete item or stream ofcontent 120 to a visitor that has started its visitation of the hostafter the start of the content 120 has been transmitted to othervisitors, resulting in the content 120 being delayed to thelate-arriving visitor relative to the other visitors. In otherimplementations, the functionality of the content storage module 314 maybe provided in a separate distribution server.

The incentive/award module 316 may provide various incentives, awards,or recognition to users based on various aspects of hosting and/orreceiving content 120. For example, the incentive/award module 316 mayprovide recognition of a host for the most visits by another user oversome timer period, the total distance over which content 120 wastransmitted to a visitor, the highest number of “likes” or positivecomments from visitors regarding an item or stream of content 120. Fromthe perspective of the visitor, recognition could be provided in lightof the highest number of different hosts or “places” visited, thedistances involved in those visits, and so on. In one example,recognition of these milestones may be published via the social network110. The incentive/award module 316 may also provide or designate moresubstantive incentives or awards, such as cash awards or credits foremploying the content-sharing service of the communication system 100.

FIGS. 4A, 4B, and 4C are communication diagrams illustrating examplemethods 400A, 400B, and 400C (collectively, methods 400) for sharingcontent using notification through a social network, such as the socialnetwork 110 of the communication network 100 of FIG. 1. However, othercommunication systems utilizing different components or systems mayemploy the methods depicted in FIGS. 4A through 4C in other examples.Further, alternatives of each of the methods 400 may omit one or moreoperations and communications described in FIGS. 4A through 4C, or mayadd other operations and communications not shown therein. In addition,each of the methods 400 may be encoded as instructions on anon-transitory computer-readable storage medium, such as, for example,an integrated circuit, magnetic disk, or optical disk, which arereadable and executable by one or more computers or other processingsystems, such as the user devices 200 of FIG. 2 and the server 300 ofFIG. 3.

In one example, prior to execution of the example methods 400 of FIGS.4A and 4B, a plurality of user devices 200 may register for the abilityto share content 120 in conjunction with the use of a social network110. In one example, this registration may occur as the result of asoftware application being installed and executed on each of the userdevices 200. Further, as a part of the installation process, theapplication may ask the user of the device 200 for informationregarding, for example, the user, the user's involvement with the socialnetwork 110, and the interest level of the user in various types ofcontent 120. Examples of the desired information, include, but are notlimited to, the user's name and other identifying information, theuser's identifier within the social network 100, and the formats,subject matter, and other characteristics of the user's favorite ordesired content 120. Such information may be stored in the user device200, the server device 300, or another device or database of thecommunication system 100 of FIG. 1. In some implementations, thisinformation may also be used to gather further data regarding thehistorical habits of the user regarding the types of content 120received, the particular time periods in which the user accessed thecontent 120, and the like. This information may be employed as describedabove to control or direct the sharing of content among the user devices200. The method 400C of FIG. 4C denotes such a registration operation,which is described more fully below.

In the example method 400A of FIG. 4A, a device 200, under the directionof a user, captures or generates content 120 (operation 402), such asone or more still images, textual data, graphical data, audio data,and/or video data. In some examples discussed below, particular emphasisis placed on the sharing of a video data stream, but the scope of theembodiments described herein is not limited to video data.

In some examples, the user device 200 may also detect a user actionrelated to the content 120 captured or generated (operation 404). Whilethe user action is depicted in FIG. 4A as occurring after the capture ofthe content 120, such an order is not mandated, as the user actions mayoccur before and/or after the capture or generation of the content 120.Such an action may be termed a “gesture”, which in one instance mayserve as a trigger for the sharing of the content 120. Possible gesturesmay encompass any of a number of user actions, such as the changing of ageographic location, as detected by the location service module 204and/or the environment detection module 206. In one implementation, agesture may include the actual capturing or generation of the content120, such as the taking of a photo or video, or the posting of thecontent 120 to the social network 110. In another instance, the gesturemay be the initiation of some other action involving the social network110, such as a social network status, comment or “like”, friend requestor acceptance, the creation of a photo album, or the like, that is notspecifically related to the content 120 in the social network 110,possibly accompanied with a location “tag” or metadata. Furthermore, agesture may be an action of another person connected to the socialnetwork 110, such as a friend or family member of the user of the device200. Such actions may include the viewing of content 120 posted to thesocial network 110, the posting of content 120 to a portion of thesocial network 110 associated with the user (for example, the user's“wall”), comments regarding the user, and so forth. In another example,the gesture may be an explicit indication by the user via the userinterface module 202 to share the content 120 as a host. Additionally, agesture may include the hosting of content 120 to another visitor.

In response to capturing the content 120, and possibly also in responseto some additional user action, the device 200 of the potential hosttransmits a gesture indication (operation 406) to a server 300. In oneimplementation, the gesture indication 406 indicates that the device 200of the potential host has captured (or is in the process of capturing)content 120 that may be shared with visitors. In response, the server300 determines potential visitors that may be interested in “visiting”the host (operation 408), thus receiving the captured or generatedcontent 120. In one example, the server 300 employs informationpreviously received from the social network 110 regarding friends,family members, and possibly others of the potential host, and use thatinformation to identify the potential visitors. In addition, the server300 may also employ user preference information of the potentialvisitors to further determine which of the potential visitors may havean interest in receiving the captured or generated content 120.

In response to determining the potential visitors, the server 300 maythen transmit an availability notification (operation 410) to each ofthe potential visitors identified. As a result, a gesture by thepotential host may be reflected in a notification to a potentialvisitor, such as a notification provided via the social network 110, orby way of an application executing on the user device 200 of thepotential visitor. The availability notification, in one example,identifies the potential host in at least one of a number of ways, suchas an individual host, as a current location of the potential host (forexample, a city or neighborhood), an identity of a particular group inwhich the host is a member, and/or the nature of the content 120 to beshared. In one example, the availability notifications are providedthrough the application that provides the content-sharing capability onthe devices 200. In a second example, the availability notifications areprovided by way of the social network 110. After receiving theavailability notification at their respective devices 200, thosepotential visitors interested in receiving the content 120 may initiatea visit request (operation 412) to be transmitted from the device 200 ofthe visitor to the server 300.

Responsive to receiving the one or more visitor requests, the server 300may transmit at least one host invitation to the device 200 of thepotential host (operation 414) for presentation to the potential host.In one example, the server 300 may transmit a single host invitation tothe device 200 of the potential host when at least one potential visitorhas issued a visit request 412. In another implementation, the server300 may transmit a host invitation for each visit request received. Theserver 300 may also indicate the identity of each potential visitor inthe host invitation 414.

In reply to the host invitation 414 presented to the potential host, thedevice 200 of the potential host may return a host response 418 to theserver 300 (operation 416) at the initiation of the potential host. Ifthe potential host decides not to fulfill the role of a host, the server300 may then inform the devices 200 of the potential visitors that thecontent 120 will not be shared (not shown in FIG. 4A). If, instead, thepotential host decides to become a host for the content 120, the server300 may then determine or select one or more distribution servers bywhich to forward the content to the devices 200 of the visitors(operation 418). Such a selection may be based on a number of factors,including, but not limited to, the number of visitors to receive thecontent 120, the communication bandwidth required to transmit thecontent 120, and the communication capabilities of the communicationnetwork 106, the distribution servers, and the receiving devices 200. Anexample method by which the distribution server is selected is discussedbelow in conjunction with FIG. 5. In one example, the distributionserver determination may be performed within the server 300, while inother cases, this operation may be provided by way of a separate devicewithin the communication network 106 (FIG. 1). Furthermore, the server300 may select one or more distribution servers from a dynamicallygenerated list of servers.

Once the server 300 selects the one or more distribution servers, theserver 300 may provide a distribution server indication to both thedevice 200 of the host (operation 420A) and the devices 200 for each ofthe visitors (operation 420B). In one example, the distribution serverindications allow each of the devices 200 to engage in communicationwith the correct server to transmit or receive the content 120, asappropriate. In response to receiving the distribution serverindication, the device 200 of the host initiates distribution of thecontent 120 via the indicated server (operation 422).

In some implementations, the content 120 distributed to the visitors maybe the content 120 currently being captured and transmitted by thedevice 200 of the host. In other embodiments, the visitor may beingreceiving the content 120 at the beginning of the capture or generationof the content 120 after the content 120 has been stored or cached atthe device 200 of the host, or on a server of the communication network106. Further, the distribution of the content 120 may be controlled byeach visitor via DVR-like commands, such as rewind, fast-forward, pause,and so on.

In another implementation, multiple different streams or items ofcontent 120 from multiple hosts may be made available to one or morevisitors. As such, the visitor may view the multiple streams or items ofcontent 120 concurrently or simultaneously, such as by way of “tiled” or“picture-in-picture” view. In one example, the multiple sources ofcontent 120 may reflect different angles or points of view of the sameevent or location.

In one example, visitors aware of the content 120, whether or notactually visiting the host, may inform their friends and other contactsvia the social network 110 of the content 120 being hosted by anotheruser. As a result, “friends of friends” not connected directly to thehost of the content 120 also may become visitors of the host. Moreover,the “friends of friends” visitors may also notify additional friends ofthe same content 120. This notification process may continueindefinitely, possibly resulting in a large number of visitors for thehost based on the social network 110. In other implementations, visitsto one or more hosts may be open or available to most or any potentialvisitors, including, for example, anonymous users and users employingaliases or pseudonyms.

In an embodiment, any and/or all of the communications from the server300 to the hosts 200, such as the availability notification (operation410), the host invitation 414, and/or the distribution serverindications (operation 420) may be issued according to a pushnotification mechanism, such as the Cloud-To-Device Messaging (C2DM)messaging framework provided by Google® Inc., or the device pushnotification channels supported by Apple® Inc.

FIG. 4B provides another example method 400B for the sharing of content120 captured or generated at a potential host device 200. The method400B is similar in several respects to the method 400A of FIG. 4A,described above. However, instead of waiting to issue the hostinvitation (operation 414) until at least one visit request has beenreceived from a device 200 of a potential visitor, the server 300transmits the host invitation in response to receiving the gestureindication 406 from the device 200 of the potential host. Thereafter,when an affirmative host response is received (operation 416) indicatingthat the potential host agrees to that role, the server then determinesthe potential visitors 408 (operation 408) and notifies the identifiedpotential visitors accordingly (operation 410). In another example, ifthe host response (operation 416) indicates that the potential host doesnot wish to host visitors, the selection of potential visitors(operation 408) and the transmission of associated availabilitynotifications (operation 410) need not occur.

In a related example, the issuance of the host invitation (operation414) may occur prior to the capture of any content (operation 402). Forinstance, at least some of multiple devices 200 may produce gestureindications (operation 406) indicating their current location. Based ona particular location being of interest (say, the location of anewsworthy event), host invitations (operation 414) may be issued tothose devices 200 corresponding to the location of interest. In afurther embodiment, the host invitations (operation 414) may be issuedto devices 200 that have not issued a gesture indication (operation406), wherein the host invitation (operation 414) indicates a particularlocation of interest, requesting host responses (operation 416) fromthose devices currently positioned at the requested location.Thereafter, a user willing to serve as a host may begin the capture ofcontent (operation 402) for transmission to one or more visitor devices200.

FIG. 4C is a communication diagram of yet another example method 400Cfor content sharing. The method 400C is similar to the method 400B ofFIG. 4B, except that no availability notifications (operation 410) andvisit requests (operation 412) are transmitted or received. Instead, theuser preferences and related information discussed above may specify theformat and types of content in which a potential visitor is interested,as well as the potential hosts from which the user may receive thecontent 120. The server 300 may retrieve such information from the userby way of a user registration (operation 401), which may occur when theuser first causes the application to be executed. As a result, theserver 300 may determine the potential visitors (operation 408) for aparticular item or stream of content 120 based on that information andproceed to determine the one or more distribution servers to be used(operation 418), and then provide distribution server indications toboth the device 200 of the host (operation 420A) and the devices 200 ofthe visitors (operation 420B).

As mentioned above, with respect to user registration (operation 401),the user may indicate the types of content 120 of interest to the user,and other information relating to the content 120. For example, the usermay designate the potential hosts in which he is interested (possiblytermed as “following” that host), content 120 associated with aparticular geographic area or region, content 120 representative of aparticular topic, and content 120 that may be presented as part of aparticular news feed. Furthermore, a selection of a particular type ofcontent 120 may be conditioned by a time limit, such as for example,over the next day or week.

In other examples similar to those illustrated in FIGS. 4B and 4C, ahost invitation (operation 414) and host response (operation 416) maynot be necessary. For example, if the potential host of content 120 isan individual or an entity, such as a news organization, that is alwayswilling to (or capable of) serving as a host for any new content 120generated or received at the device 200 of the host, the informationalexchange embodied in the host invitation and host response may beunnecessary. Thus, after the capture of content (operation 402) and/orthe detection of a related user action (operation 404), thus causing agesture indication to be transmitted to the server 300 (operation 406),the potential visitors may be determined (operation 408), thedistribution server selected (operation 418), the distribution serverindications issued (operation 420), and the content distributioninitiated (operation 422), as discussed above.

In one implementation, potential visitors may be determined by way ofpresenting indications of potential items or streams of content 120 forselection by the potential visitors, such as by way of the socialnetwork 110. For example, a webpage associated with the social network110 may present a number of “featured” items or areas of content 120,such as different types of news, sports, and the like, or differentgeographic areas, such as specific cities, states, or countries. Afterbeing presented with these options, the potential visitor may select oneor more of the features items for reception and viewing. In one example,such selections may only apply to a one-time item of content 120, afterwhich such selections may have no effect for that visitor.

In other examples, the determination of one or more distribution servers(operation 418) and the associated distribution server indications(operation 420) may not be implemented if the distribution servers areknown in advance to the various devices 200 involved in the sharing ofthe content 120.

While FIGS. 4A, 4B, and 4C reflect separate devices 200 for hosts andvisitors, a single device 200 may serve as both a host and a visitor fordifferent items or streams of content 120. For example, the sharing ofcontent between two devices 200 may occur simultaneously therebetweenusing the various concepts described above, although employing a device200 as a host device and a visitor device is not restricted to abidirectional, one-to-one sharing of content 120.

FIG. 5 is a block diagram of an example content distribution system 500in which the device 200 of the host transmits content 510 to adistribution server 502A, which in turn distributes the content 510 toone or more devices 200 for visitors of the host. In one example, thedistribution server 502A is selected as part of the example methods400A, 400B, and 400C of FIGS. 4A, 4B, and 4C, respectively (operation422). As discussed earlier, the distribution server selection module 312of the server 300 (FIG. 3) may perform the selection of the distributionserver 502A. In other examples, other distribution servers 502B and 502Cmay be selected for distribution of the content 510 to other visitordevices 200 by either the distribution server selection module 312 or aseparate traffic management device 504, shown in FIG. 5. Further, asdescribed below, the distribution server selection module 312 in theserver 300 (FIG. 3) or the traffic management device 504 may communicatewith the distribution server 502A by way of a control connection 520 todetermine whether more or fewer distribution servers may be desirablefor distributing the content 510. In the implementation depicted in FIG.5, the multiple distribution servers 502 may constitute at least aportion of a distribution server farm 501. While the server farm 501 ofFIG. 5 explicitly illustrates only three distribution servers 502, ahigher number of such servers 502 may be included in the server farm 501in other embodiments.

In one implementation, the first distribution server 502A may be termeda “canonical server” for its status as the primary distribution serveremployed for sharing of the content 510. In one example, the canonicalserver 502A may not be capable of distributing the content 510 (forexample, an audio/video stream) to each of the visiting devices 200. Asa result, the canonical server 502A may keep the traffic managementdevice 504 apprised of the visitor devices 200 currently receiving thecontent 510, as well as any other information that may aid the trafficmanagement device 504 in enlisting another distribution server 502B,502C into service for the distribution of the content 510.

In one example, the canonical distribution server 502A may betransferring multiple streams of content 510 simultaneously, with noother distribution servers 502B, 502C involved. While performing thesetransfers, the canonical distribution server 502A may determine that thenumber of visitor devices 200 receiving a particular stream of content510 has increased beyond a predetermined threshold. In response, thecanonical distribution server 502A may inform the traffic managementdevice 504 of the condition, causing the traffic management device 504to instruct the canonical server 502A to assign one or more of theremaining distribution servers 502B, 502C to additional visitor devices200 requesting the content 510. In one example, the traffic managementdevice 504 determines and informs the canonical server 502A which of theremaining distribution servers 502B, 502C are to be used. Suchinformation may be based on random selection, consideration of currenttraffic levels regarding the content 510, and other factors.

In response to the selection of at least one additional distributionserver 502B, 502C, the canonical server 502A directs the incomingcontent 510 to the selected distribution server 502B, 502C. In oneimplementation, the canonical server 502A establishes a proxy connectionwith the selected distribution server 502B, 502C, thereby accessing theselected distribution server 502B, 502C as a pseudo-visitor device 200.In addition, the canonical distribution server 502A, the trafficmanagement device 504, the original server 300, or another deviceinforms each newly-joining visitor device 200 of the identity of thedistribution server 502B, 502C assigned thereto.

As a result, the canonical distribution server 502A acts as the singlereceiving point for the content 510 from the host device 200. Inaddition, the canonical server 502A then delivers the content 510directly to one or more visitor devices 200, and may direct the content510 to one or more additional servers 502B, 502C, which in turn transferthe content 510 directly to additional visitor devices 200. Therefore,the maximum number of distribution servers 502 separating the device 200for the host and each of the devices 200 of the visitors may be two,thereby reducing the overall latency incurred in the transmission of thecontent 510.

Thereafter, as fewer visitors decide to continue to receive a particularstream of content 510, the number of distribution servers 502 utilizedto forward the content to devices 200 of the visitors may be reducedaccordingly, possibly to the point at which the canonical server 502A isonly forwarding the content 510 directly to a number of devices 200instead of also forwarding the content 510 to one or more of theremaining distribution servers 502B, 502C of the server farm 501.

FIGS. 6A through 6J provide screen views 600A through 600J of an exampleuser interface of a user device 200 as provided by an application thatfacilitates the sharing of content among users of a social network, asdescribed above. In the following examples, the user interface isprovided by an application executing on a mobile device, such as a“smart” phone or PDA, although the same or similar applications forcontent sharing may be executed on other hardware platforms, such asdesktop and laptop computers, table computers, game systems,televisions, and so on.

FIG. 6A exhibits an example screen view 600A displayed on a device 200for a potential visitor. In one example, the screen view 600A representsa “profile” page of the user, which displays a “visit” button 602 for aspecific friend of the user. In one example, the profile page shown inFIG. 6A is accessed by way of a preceding “friends” list listing thefriend shown in the screen view 600A, along with other friends of theuser of the device 200. To return to the friends listing, the user maysimply activate the “friends” button 603 shown in the screen view 600A.In the specific example of FIG. 6A, the screen view 600A may alsodisplay various items of content, such as individual photos, a photoalbum, still images from video clips, and the like.

Presuming the user of the device 200 activates the “visit” button 602shown in the screen view 600A, the application produces a confirmationpage, shown in a screen view 600B of FIG. 6B. The screen view 600Bprovides a “visit” confirmation button 604 for confirming the request tovisit the friend, and a “cancel” button 606 to cancel the request.

Presuming the user activates the “visit” confirmation button 604, thedevice 200 may present the screen view 600C of FIG. 6C, which informsthe user by way of one or more status indicators 608A, 608B that thedevice 200 has sent the visitation request, and is awaiting approval ofthe requested visit. In the example of FIG. 6C, the screen view 600C mayalso display photo albums 610 and/or other content of the user.

Once the device 200 has received approval for the visit, content fromthe friend, serving as the host for the visiting user, is displayed tothe user. As depicted in the screen view 600D of FIG. 6D, content 614(in this case, a video stream) is presented to the user, and a visitingindicator 612 is displayed to remind the user that the device 200 is ina visiting mode. To terminate the visiting mode, the user may simplyactivate a “done” button 616 displayed in the screen view 600D.

Once the visiting mode is terminated, the user may be presented with ascreen view 600E (presented in FIG. 6E) confirming termination of thevisitation by way of a “done visiting” indication 617. In addition, theuser may indicate its view of the content by way of “liking” the contenton the social network 110 (FIG. 1) via a “like” button 618 or commentingon the content by activation of a “comment” button 620 that provides thecomment on the social network 110. In addition, the screen view 600E maypresent profile photos 622 of one or more friends which, when activated,may cause the device 200 to present a screen associated specificallywith the selected friend to allow the user to visit that friend.

In a separate example, FIG. 6F presents a screen view 600F seen by thepotential visiting user when using the application. The screen view 600Findicates that a friend has begun hosting content, and asks if the userwould like to visit or ignore the friend by way of a “visit” button 626and an “ignore” button 624, respectively. In one example, if the useractivates the “visit” button 626, the user may be presented with thescreen view 600C of FIG. 6C, informing the user that the device 200 isawaiting approval to visit the friend.

While FIGS. 6A through 6F describe various screen views 600A through600F that may be presented to a potential visitor, FIGS. 6G through 6Jpresent screen views 600G through 600J from the perspective of apotential host. For example, FIG. 6G presents a screen view 600G of thepotential host's profile page, which provides a “host” button 628 that,when activated, initiates the process of placing the device 200 of thehost in a hosting mode, thus transmitting content to those visitors thatare interested in the content.

Upon activation of the “host” button 628, a screen view 600H of FIG. 6Hrequests confirmation by presenting a second “host” button 630 and a“cancel” button 632. In one example, cancellation of the hosting requestreturns the user to the profile page screen view 600G of FIG. 6G.

If, instead, the user activates the second “host” button 630, the device200 of the host begins a hosting session, and presents a screen view600I (shown in FIG. 6I) displaying the content 636 that the host ispresenting to other users. The screen view 600I also provides a“hosting” indicator 634 to ensure the user is aware that he isbroadcasting to others, and also displays a “profile” button 638 thatwould return the user to the profile page of screen view 600G of FIG.6G, thus ending the hosting session. In one example, those friendsactually visiting (i.e., receiving the content 636) may be denoted onthe screen view 600I, such as by way of photos or icons associated witheach of the friends visiting.

Presuming the host has activated the “profile” button 638 of the screenview 600I, the device may present the “profile” page of the user inresponse. At some point thereafter, the user may then receive a requestfrom a friend to begin hosting another session. To indicate the request,the device 200 of the host may present a screen view 600J shown in FIG.6J, in which the requesting friend is identified, a “host” button 642 ispresented to allow the host to begin the session, and an “ignore” button640 is provided to allow the host to ignore the request. Presuming thehost activates the “host” button 642, the device 200 may present anotherhosting confirmation screen view, such as the screen view 600H of FIG.6H.

In the examples noted above, a device 200 may receive informationregarding who is hosting, who is visiting, and so on by way ofinformation passed between the server 300 and the devices 200 by way ofthe separate notification channel described above.

FIGS. 7A through 7O provide screen views 700A through 700O of exampleweb-based user interfaces presented by way of a web browser for visitinga host in a variety of ways. More specifically, FIGS. 7A through 7D,FIG. 7N, and FIG. 7O present screen views of a content-sharingapplication (referred to the drawings as “Blue”, developed by ColorLabs, Inc.) as embedded in a “canvas” of a social networking webpage (inthis case, Facebook). FIGS. 7E through 7M depict screen views of thesocial networking website not involving the use of the embeddingenvironment. In other examples, the content-sharing application may beaccessed as a web application directly outside of the social networkingcontext.

FIG. 7A presents an example screen view 700A of the content-sharingapplication embedded within a social network webpage, with theapplication supplying a profile page providing a potential hostindication 704 with an associate “visit” button 702 that, whenactivated, initiates a process in which the user may visit the indicatedhost. As shown in FIG. 7A, the screen view 700A may also provide one ormore “album” summary areas 706, in which the album may include multipleitems or streams of content for viewing.

Similarly, FIG. 7B illustrates an example screen view 700B of a webpagefor an album. In one example, this webpage may be accessed by way ofactivating the album summary area 706 of the screen view 700A of FIG.7A. In the screen view 700B, the album title 710 (“Work Food”) ispresented, along with the individual content items 712 that may beactivated for viewing. Also provided is another “visit” button 708 that,when activated, will initiate a process by which the user may visit atleast one of the listed potential hosts.

Presuming the visitation process has been initiated by activating one ofthe “visit” buttons 702, 708, as described above, the application maypresent the screen view 700C of FIG. 7C. Therein, content 714 may bepresented to the visiting user, thereby experiencing what the host isexperiencing. In the screen view 700C, the identity of the host, and anindication that the visitation is in progress, may be provided in atitle area 716. In one example, the identity of each of the visitors mayalso be presented by way of an icon 718 or photo corresponding to eachof the visitors. In one example, this information may be provided in thescreen view 700C in real-time by way of a push notification channel,such as one that may employ a “hanging Get” protocol. In oneimplementation, the content 714 may be presented to the user via theMotion JPEG (M-JPEG) format.

FIG. 7D depicts an example screen view 700D of a “push notification”employing a push notification channel, such as the one mentioned above.In this example, the push notification informs the user that a friend ishosting content, specifically by way of a pop-up notification 720, whichmay provide a “visit” button 722. In one implementation, in response tothe user activating the “visit” button 722, the content 714 sourced bythe host may be presented, such as via the screen view 700C of FIG. 7C.

FIG. 7E presents an example screen view 700E of a hosting notificationon the user's social networking (Facebook) webpage. In the screen view700E, the hosting notification is presented as a “gesture” 724 (asdescribed earlier) in a “ticker” of the social networking webpage. Inone example, upon activation of the gesture 724, a pop-up area 726 maybe presented by which the user may visit the indicated host, as shown inthe screen view 700F of FIG. 7F. More specifically, the pop-up area 726may include a “visit” link 730 to initiate a visit of the host indicatedin the pop-up area 726. In an example, activating the link 730 may causethe presentation of a webpage for the application embedded in the canvasof the social networking site, such as shown in the screen view 700C ofFIG. 7C. Also shown in the screen view 700F are “like” and “comment”links 732 associated with the social network site, whereby the user mayprovide input regarding the host or the content to be viewed.

In an alternative to the “visit” link 730, the user may visit the hostby way of a “play” button 728 of the pop-up area 726, in which case thecontent sourced by the host may be provided “inline” within the currentsocial network webpage. An example of such content is presented in anexample screen view 700G of FIG. 7G. Therein, a pop-up window 734associated with the gesture 724 provides the content 736 being suppliedby the host. In one implementation, a Flash® player is employed toprovide the content 736 in an inline manner.

FIG. 7H presents an example screen view 700H illustrating a hostingnotification by way of a “news feed” of the social network site. Morespecifically, a “story” 738 of the news feed may indicate that aparticular friend of the user is currently hosting, and provide a“visit” link 740 to visit using the embedded application within thesocial network site, a “play” button 742 to visit inline within the newsfeed, and like/comment links 744, similar to those respective featuresof the pop-up area 726 of FIG. 7F.

FIGS. 7I through 7M provide example screen views 700I-700M,respectively, of a social network webpage displaying various states of asocial network webpage of the user visiting a host as presented by aFlash player. As shown in the screen view 700I of FIG. 7I, once a userhas initiated an inline visit via a story, as described above withrespect to FIG. 7H, the Flash player provides an informational window746 on the webpage indicating that the visit is being prepared. In oneexample, the screen view 700I may be shown immediately after the userinitiates the visit. Thereafter, the screen view 700J of FIG. 7J maypresent a second informational window 748 once the Flash player hascontacted a server (such as the server 300 of FIG. 3), providinginformation about the host, such as, for example, a name and photo oricon. FIG. 7K depicts an example screen view 700K of the same webpageafter the visit has successfully completed, providing a thirdinformational window 750 announcing completion of the visit, possiblewith a button 752 allowing the user to visit the embedded (canvas)application. The webpage may also alert the user in cases in which thevisit was not successful, such as the example screen view 700L of FIG.7L, which indicates that the potential host was unavailable, andpossibly provides a button 756 allowing the user to restart thevisitation attempt. In FIG. 7M, an example screen view 700M of thewebpage informs the user of a network error, and possibly provides abutton 760 to allow the user to retry the visit.

FIGS. 7N and 7O present example screen views 700N and 700O,respectively, reflecting visitation states that the embedded webapplication, as discussed in detail above, may render. In one example,these states may be provided by the M-JPEG player mentioned above. Thescreen view 700N, for instance, may be presented to the user in responseto the user initiating a visit via the embedded application, such as isdescribed above in conjunction with FIGS. 7A through 7C, with the screenview 700N displaying a message 762 indicating that the connection withthe host is being formed. Once the visit is completed, the embeddedapplication may provide the screen view 700O of FIG. 7O, which mayprovide a completion message 764 and may list attendees of the visit byway of icons or photo 766, any of which the user may activate toinitiate a visit therewith.

While FIGS. 6A through 6J and FIGS. 7A through 7O provide severalexamples of user interfaces associated with the embodiments describedherein, many other examples providing the functionality described hereinmay be employed in other implementations.

As a result of at least some of the embodiments discussed herein,sharing of content, such as still images, video clips, audio segments,and textual data, may be shared easily among a number of user deviceswhile employing a social network, such as Facebook®. For example,identification of possible visitors to a host may be accomplished by wayof the social network, such as by way of identifying friends, familymembers, and others connected in some way to the host via the socialnetwork. In some implementations, the host may be informed of potentialvisitors desiring of a visit to the host, and potential visitors may beinformed on a host currently providing content for sharing.Additionally, positive recognition for past or current activities by auser as a host and/or visitor may also be provided via the socialnetwork. Other ways of engaging in the sharing of content using thesocial network, such as by notifying multiple levels of friends in thesocial network of the content, as described above, may be utilized also.Access to the shared content, as well as various functions relatedthereto, may be supplied via an application executing on a user devicespecifically intended for the sharing of content, as well as the socialnetwork itself, thus allowing each user to engage in the sharing ofcontent, either as a host or visitor, from a multitude of user devicesand execution platforms.

Modules, Components, and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A hardware module is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client, or server computersystem) or one or more hardware modules of a computer system (e.g., aprocessor or a group of processors) may be configured by software (e.g.,an application or application portion) as a hardware module thatoperates to perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarilyconfigured (e.g., programmed) to operate in a certain manner and/or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplesuch hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or processors or processor-implementedmodules. The performance of certain of the operations may be distributedamong the one or more processors, not only residing within a singlemachine, but deployed across a number of machines. In some exampleembodiments, the processor or processors may be located in a singlelocation (e.g., within a home environment, an office environment, or asa server farm), while in other embodiments the processors may bedistributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), these operations being accessible via anetwork (e.g., the Internet) and via one or more appropriate interfaces(e.g., APIs).

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, or software, or in combinationsthereof. Example embodiments may be implemented using a computer programproduct (e.g., a computer program tangibly embodied in an informationcarrier in a machine-readable medium) for execution by, or to controlthe operation of, data processing apparatus (e.g., a programmableprocessor, a computer, or multiple computers).

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram can be deployed to be executed on one computer or on multiplecomputers at one site or distributed across multiple sites andinterconnected by a communications network.

In example embodiments, operations may be performed by one or moreprogrammable processors executing a computer program to performfunctions by operating on input data and generating output. Methodoperations can also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry(e.g., a field programmable gate array (FPGA) or an application-specificintegrated circuit (ASIC)).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on their respectivecomputers and having a client-server relationship to each other. Inembodiments deploying a programmable computing system, it will beappreciated that both hardware and software architectures may beconsidered. Specifically, it will be appreciated that the choice ofwhether to implement certain functionality in permanently configuredhardware (e.g., an ASIC), in temporarily configured hardware (e.g., acombination of software and a programmable processor), or a combinationof permanently and temporarily configured hardware may be a designchoice. Below are set forth hardware (e.g., machine) and softwarearchitectures that may be deployed in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 8 is a block diagram of a machine in the example form of a computersystem 800 within which instructions for causing the machine to performany one or more of the methodologies discussed herein may be executed.In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting instructions (sequential or otherwise) that specify actions tobe taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The example computer system 800 includes a processor 802 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU), orboth), a main memory 804, and a static memory 806, which communicatewith each other via a bus 808. The computer system 800 may furtherinclude a video display unit 810 (e.g., a liquid crystal display (LCD)or a cathode ray tube (CRT)). The computer system 800 also includes analphanumeric input device 812 (e.g., a keyboard), a user interface (UI)navigation device 814 (e.g., a mouse), a disk drive unit 816, a signalgeneration device 818 (e.g., a speaker), and a network interface device820. The computer system 800 may also include a environmental inputdevice 826 that may provide a number of inputs describing theenvironment in which the computer system 800 or another device exists,including, but not limited to, any of a Global Positioning Sensing (GPS)receiver, a temperature sensor, a light sensor, a still photo or videocamera, an audio sensor (e.g., a microphone), a velocity sensor, agyroscope, an accelerometer, and a compass.

Machine-Readable Medium

The disk drive unit 816 includes a machine-readable medium 822 on whichis stored one or more sets of data structures and instructions 824(e.g., software) embodying or utilized by any one or more of themethodologies or functions described herein. The instructions 824 mayalso reside, completely or at least partially, within the main memory804 and/or within the processor 802 during execution thereof by thecomputer system 800, the main memory 804 and the processor 802 alsoconstituting machine-readable media.

While the machine-readable medium 822 is shown in an example embodimentto be a single medium, the term “machine-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore instructions 824 or data structures. The term “non-transitorymachine-readable medium” shall also be taken to include any tangiblemedium that is capable of storing, encoding, or carrying instructionsfor execution by the machine and that cause the machine to perform anyone or more of the methodologies of the present subject matter, or thatis capable of storing, encoding, or carrying data structures utilized byor associated with such instructions. The term “non-transitorymachine-readable medium” shall accordingly be taken to include, but notbe limited to, solid-state memories, and optical and magnetic media.Specific examples of non-transitory machine-readable media include, butare not limited to, non-volatile memory, including by way of example,semiconductor memory devices (e.g., Erasable Programmable Read-OnlyMemory (EPROM), Electrically Erasable Programmable Read-Only Memory(EEPROM), and flash memory devices), magnetic disks such as internalhard disks and removable disks, magneto-optical disks, and CD-ROM andDVD-ROM disks.

Transmission Medium

The instructions 824 may further be transmitted or received over acomputer network 850 using a transmission medium. The instructions 824may be transmitted using the network interface device 820 and any one ofa number of well-known transfer protocols (e.g., HTTP). Examples ofcommunication networks include a local area network (LAN), a wide areanetwork (WAN), the Internet, mobile telephone networks, Plain OldTelephone Service (POTS) networks, and wireless data networks (e.g.,WiFi and WiMAX networks). The term “transmission medium” shall be takento include any intangible medium that is capable of storing, encoding,or carrying instructions for execution by the machine, and includesdigital or analog communications signals or other intangible media tofacilitate communication of such software.

CONCLUSION

Thus, a method and system to share content among several communicationdevices have been described. Although the present subject matter hasbeen described with reference to specific example embodiments, it willbe evident that various modifications and changes may be made to theseembodiments without departing from the broader scope of the subjectmatter. For example, while the majority of the discussion above notesthe use of the embodiments with respect to general-purpose computersystems and applications, other software- or firmware-based systems,such as electronic products and systems employing embedded firmware, mayalso be developed in a similar manner to that discussed herein.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense. The accompanying drawingsthat form a part hereof, show by way of illustration, and not oflimitation, specific embodiments in which the subject matter may bepracticed. The embodiments illustrated are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed herein. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. ThisDetailed Description, therefore, is not to be taken in a limiting sense.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

All publications, patents, and patent documents referred to in thisdocument are incorporated by reference herein in their entirety, asthough individually incorporated by reference. In the event ofinconsistent usages between this document and those documents soincorporated by reference, the usage in the incorporated reference(s)should be considered supplementary to that of this document; forirreconcilable inconsistencies, the usage in this document controls.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of“at least one” or “one or more.” In this document,the term “or” is used to refer to a nonexclusive or, such that “A or B”includes “A but not B,” “B but not A,” and “A and B,” unless otherwiseindicated.

What is claimed is:
 1. A method comprising: receiving an indication viaa user interface in a first mobile device to begin recording live videoon the first mobile device; causing the recording of live video by thefirst mobile device in response to the receiving of the indication;displaying the live video in the user interface as it is being recorded;detecting, during the displaying of the live video, via the userinterface, a gesture by a user of the first mobile device; in responseto the detection of the gesture, causing the broadcasting of the livevideo as it is being recorded to a plurality of mobile devices otherthan the first mobile device; displaying identifications, in the userinterface along with the live video, of a plurality of userscorresponding to the plurality of mobile device other than the firstmobile device to which the live video is being broadcast.
 2. The methodof claim 1, further comprising: upon receiving an indication that one ofthe plurality of users wishes to terminate viewing of the live videobroadcast, removing the indication in the user interface correspondingto the one of the plurality of users.
 3. The method of claim 2, whereinthe indication that the one of the plurality of users wishes toterminate viewing of the live video broadcast is an indication that abutton indicating that a visit is complete has been selected.
 4. Themethod of claim 1, further comprising presenting a confirmation buttonto the user of the first mobile device and the causing the broadcastingis performed in response to receipt of an indication that theconfirmation button has been selected.
 5. The method of claim 1, whereinthe identifications include photos of the plurality of users.
 6. Themethod of claim 1, wherein the user interface further containsindications of relationships between the user of the first mobile deviceand other users in the social network service.
 7. A first mobile devicecomprising: a hardware processor; a computer-readable medium havinginstructions stored thereon, which, when executed by the processor,cause the system to: receive an indication via a user interface in afirst mobile device to begin recording live video on the first mobiledevice; cause the recording of live video by the first mobile device inresponse to the receiving of the indication; display the live video inthe user interface as it is being recorded; detect, during thedisplaying of the live video, via the user interface, a gesture by auser of the first mobile device; in response to the detection of thegesture, cause the broadcasting of the live video as it is beingrecorded to a plurality of mobile devices other than the first mobiledevice; display identifications, in the user interface along with thelive video, of a plurality of users corresponding to the plurality ofmobile device other than the first mobile device to which the live videois being broadcast.
 8. The first mobile device of claim 7, wherein theinstructions, when executed on by the processor, further cause theprocessor to: upon receiving an indication that one of the plurality ofusers wishes to terminate viewing of the live video broadcast, removethe indication in the user interface corresponding to the one of theplurality of users.
 9. The first mobile device of claim 8, wherein theindication that the one of the plurality of users wishes to terminateviewing of the live video broadcast is an indication that a buttonindicating that a visit is complete has been selected.
 10. The firstmobile device of claim 7, wherein the instructions, when executed on bythe processor, further cause the processor to: present a confirmationbutton to the user of the first mobile device and the causing thebroadcasting is performed in response to receipt of an indication thatthe confirmation button has been selected.
 11. The first mobile deviceof claim 7, wherein the identifications include photos of the pluralityof users.
 12. The first mobile device of claim 7, wherein the userinterface further contains indications of relationships between the userof the first mobile device and other users in the social networkservice.
 13. A non-transitory computer-readable storage mediumcomprising instructions that, when executed by at least one processor ofa machine, cause the machine to perform operations comprising: receivingan indication via a user interface in a first mobile device to beginrecording live video on the first mobile device; causing the recordingof live video by the first mobile device in response to the receiving ofthe indication; displaying the live video in the user interface as it isbeing recorded; detecting, during the displaying of the live video, viathe user interface, a gesture by a user of the first mobile device; inresponse to the detection of the gesture, causing the broadcasting ofthe live video as it is being recorded to a plurality of mobile devicesother than the first mobile device; displaying identifications, in theuser interface along with the live video, of a plurality of userscorresponding to the plurality of mobile device other than the firstmobile device to which the live video is being broadcast.
 14. Thenon-transitory computer-readable storage medium of claim 13, wherein theoperations further comprise: upon receiving an indication that one ofthe plurality of users wishes to terminate viewing of the live videobroadcast, removing the indication in the user interface correspondingto the one of the plurality of users.
 15. The non-transitorycomputer-readable storage medium of claim 14, wherein the indicationthat the one of the plurality of users wishes to terminate viewing ofthe live video broadcast is an indication that a button indicating thata visit is complete has been selected.
 16. The non-transitorycomputer-readable storage medium of claim 13, wherein the operationsfurther comprise presenting a confirmation button to the user of thefirst mobile device and the causing the broadcasting is performed inresponse to receipt of an indication that the confirmation button hasbeen selected.
 17. The non-transitory computer-readable storage mediumof claim 13, wherein the identifications include photos of the pluralityof users.